Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-35291

Unable to add ‘Create from template’ Macro to a Global Template

      NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.

      Status Update 26 October 2020

      We reviewed this bug and could see that actual root cause is coming from the fact that no "space key" is chosen when adding "create from template" macro to a Global template.

      Details of the issue are submitted to the new bug:
      https://jira.atlassian.com/browse/CONFCLOUD-70992

      New workaround :

      1. Create / edit a Global template
      2. Add "create from template" macro
      3. Make sure to add "space key" at the bottom left of the macro edit form. After that "template name" drop-down will be available.
      4. Once you create a new page based on the global template, you will need to click "edit" button for "create from template" macro to have space key updated correctly.

      Current Behaviour

      When creating or editing a Global Template and trying to add the ‘Create from template’ Macro the macro editor hangs. Dropdowns aren't responsive.

      Error message

      404 error is thrown in the browser console:

      Workaround

      1. edit regular (non-template) Confluence page and add the ‘Create from template’ Macro to it;
      2. copy the macro from the page editor;
      3. edit a Global Template and past the macro copied in previous step;
      4. save the template - the macro button will work as expected.

      Note

      If user language is not English, the workaround won't work.

            [CONFCLOUD-35291] Unable to add ‘Create from template’ Macro to a Global Template

            Not in our instance. I just tried now again and it is still going to the space I initially set. What a bummer. Can someone from Confluence check our instance? This is not going to work for us. We need to create a template off of a form to make sure our users don't miss associating it to the parent form.

            Pong Bautista added a comment - Not in our instance. I just tried now again and it is still going to the space I initially set. What a bummer. Can someone from Confluence check our instance? This is not going to work for us. We need to create a template off of a form to make sure our users don't miss associating it to the parent form.

            There has been a fix, at least in my Confluence Cloud instance. You just have to set the space to whatever in order to add it to the template, then when you actually create a page from the template it will update the space key to the one you are currently in. 

            Lissa Meade added a comment - There has been a fix, at least in my Confluence Cloud instance. You just have to set the space to whatever in order to add it to the template, then when you actually create a page from the template it will update the space key to the one you are currently in. 

            It's 2024. Has there been a fix to not require the Space Key in GLOBAL TEMPLATES? What's an alternative solution? 

            Pong Bautista added a comment - It's 2024. Has there been a fix to not require the Space Key in GLOBAL TEMPLATES? What's an alternative solution? 

            The space key, which determines which space the new pages will be created in, is a required field in order to save the macro. However, with this fix, you should now be able to browse the global templates in the dropdown without specifying the space key first.

            Hayley Howell (Inactive) added a comment - The space key, which determines which space the new pages will be created in, is a required field in order to save the macro. However, with this fix, you should now be able to browse the global templates in the dropdown without specifying the space key first.

            Thank you for fixing this issue! I don't see any change in the admin UI yet, the space key is still required and @self doesn't work. Is there something I need to do in the admin, or are we waiting for a release?

            Lissa Meade added a comment - Thank you for fixing this issue! I don't see any change in the admin UI yet, the space key is still required and @self doesn't work. Is there something I need to do in the admin, or are we waiting for a release?

            Hi everyone,

            This is Hayley from the Confluence team. This bug is now fixed and I confirmed the functionality to be working as expected. Thank you for your patience!

            Sincerely,

            Hayley

            Hayley Howell (Inactive) added a comment - Hi everyone, This is Hayley from the Confluence team. This bug is now fixed and I confirmed the functionality to be working as expected. Thank you for your patience! Sincerely, Hayley

            Ben Shuker added a comment -

            Can I assume like most bugs this will continue to be ignored, or perhaps a fix will be rolled into a more expensive licence?

            Ben Shuker added a comment - Can I assume like most bugs this will continue to be ignored, or perhaps a fix will be rolled into a more expensive licence?

            Krista Stellar added a comment - - edited

            This is listed as in progress, however that's been true for over a year. And it was reported several years ago. Templates are a powerful feature of Confluence, but without this basic ability to effectively use the create from template macro button in a global template you are hampering the options for creating smooth workflows for creating pages based upon templates.

            Would it be possible to get an update? Is this really 'in progress'?

            Krista Stellar added a comment - - edited This is listed as in progress, however that's been true for over a year. And it was reported several years ago. Templates are a powerful feature of Confluence, but without this basic ability to effectively use the create from template macro button in a global template you are hampering the options for creating smooth workflows for creating pages based upon templates. Would it be possible to get an update? Is this really 'in progress'?

            Vasi added a comment -

            2f594e586857 thank you for the thorough check. I can confirm that, indeed, we have to open edit screen of the "create from template" macro to make sure that space key is updated.
            I corrected workaround section of this bug.

            Vasi added a comment - 2f594e586857  thank you for the thorough check. I can confirm that, indeed, we have to open edit screen of the "create from template" macro to make sure that space key is updated. I corrected workaround section of this bug.

            Vasi added a comment -

            2f594e586857,

            You are right - we shouldn't specify a space key since it is a global template. Hence, this is just a workaround for now.

            I was testing this workaround earlier and I could see that when a global template is created using new workaround, "create from template" macro will be having a space key configured based on a space where page is created (as it should work ideally).

            If it doesn't work for you, would be great if you could update the Support request that you have with us at the moment and we will check further.

             

            Vasi added a comment - 2f594e586857 , You are right - we shouldn't specify a space key since it is a global template. Hence, this is just a workaround for now. I was testing this workaround earlier and I could see that when a global template is created using new workaround, "create from template" macro will be having a space key configured based on a space where page is created (as it should work ideally). If it doesn't work for you, would be great if you could update the Support request that you have with us at the moment and we will check further.  

              ele Eric Le (Inactive)
              namir Nursihah Amir (Inactive)
              Affected customers:
              44 This affects my team
              Watchers:
              64 Start watching this issue

                Created:
                Updated:
                Resolved: